12525 Automated JSF Frontend Playwright Tests#12526
Conversation
There was a problem hiding this comment.
Pull request overview
Adds a new GitHub Actions workflow to run automated Playwright-based JSF frontend tests against a containerized Dataverse instance, leveraging the external uncch-rdmc/kunai-runner test suite.
Changes:
- Introduces a CI workflow that builds and starts the Dataverse container stack via Maven and waits for API readiness.
- Checks out
uncch-rdmc/kunai-runner, installs Node/Playwright dependencies, and runs Playwright tests againsthttp://localhost:8080. - Uploads Playwright artifacts (report + traces/videos/screenshots) and Dataverse container logs for debugging.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - name: Checkout kunai-runner | ||
| uses: actions/checkout@v6 | ||
| with: | ||
| repository: uncch-rdmc/kunai-runner | ||
| path: kunai-runner | ||
|
|
There was a problem hiding this comment.
Sure. This is upstream's decision to make. It's probably a good decision too. More manual work, but outsourcing QA to an external repository is never a good idea
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Removed commented-out code for creating a Playwright test user and uploading Playwright test results.
| - name: Checkout kunai-runner | ||
| uses: actions/checkout@v7 | ||
| with: | ||
| repository: uncch-rdmc/kunai-runner |
There was a problem hiding this comment.
This (and related config below) should be changed to the place we moved it, right? Here: https://github.com/gdcc/dataverse-jsf-tests
pdurbin
left a comment
There was a problem hiding this comment.
Looks great!
I updated the docs and removed old UI tests we aren't using (Selenium and Cypress).
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
What this PR does / why we need it:
This PR introduces a GitHub Action that pulls the JSF frontend testing repository and runs it against a containerized version of Dataverse.
Which issue(s) this PR closes:
Special notes for your reviewer:
Workflow triggers, folder restrictions, etc are all preferences of upstream
Suggestions on how to test this:
Running the GitHub Action should give you a very clear picture of the tests.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
N/A
Is there a release notes update needed for this change?:
N/A
Additional documentation:
N/A